fix(filters): handle sync-flush terminated zlib streams in FlateDecode #20
+246
−144
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #16 —
TypeError: Cannot read properties of undefined (reading 'length')when extracting text from PDFs generated by PDFium.pako.inflate()silently returnsundefined(instead of throwing) for zlib streams terminated with a sync-flush marker (00 00 FF FF) instead of a proper final block and Adler-32 checksum. Some PDF generators (notably PDFium) produce these streams. Theundefinedpropagated throughFilterPipelineintoconcatenateChunks()which crashed on.length.FlateFilternow detects whenpako.inflate()returnsundefinedor throws, and falls back to recovering partial output from pako's internalInflatestate. Truly unrecoverable streams return emptyUint8Arrayrather than throwing, consistent with our lenient approach to malformed PDFs.